home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
lan
/
vlmkt2.zip
/
ODINSUP.DOC
< prev
next >
Wrap
Text File
|
1994-10-04
|
45KB
|
1,618 lines
This is the readme for ODINSUP.COM.
ODINSUP COM 33867 02-23-93 8:58a version 1.22
Modification History:
Changes from v1.01 to v1.10 beta
1. Enhanced to run with Lan Manager 2.0 and 2.1. These changes made
to allow code to run with MicroSoft's NetBeui Protocol Stack.
Use new NET.CFG parameter BUFFERED.
2. Enhanced to allow detection of 386 MicroProcessor for better
performance.
Changes from v1.10 beta to v1.21
1. Enhanced ODINSUP.COM driver from 1.0 NDIS spec to NDIS v2.0 spec.
2. Fixed a bug in a code path where a variable lacked a CS override.
Symptom seen (under a heavy load to the AS/400 (ethernet) using
PC/SUPPORT the machine would either hang or drop the
AS/400 connection).
Changes from v1.21 to v2.22
1. Changed the way ODINSUP registers as a default protocol stack.
The previous method could cause a potential problem if another
default protocol stack registered with the Link Support Layer.
PURPOSE OF ODINSUP.COM:
As part of Novell's commitment to be interoperable, ODI supports NDIS. ODI's
modular architecture allows users to support support NDIS protocol stacks.
A module called ODINSUP.COM allows NDIS protocol stacks to run unmodified
over the ODI LSL and talk to an ODI LAN driver. Now, multi-vendor network
transports like IBM's NetBEUI, DEC's LAT or 3COM's XNS can be run over a
common Dat-Link (driver) specification. For more information, read the
ODIINFO.DOC file included in this .ZIP file.
*************************************************************************
*************************NECESSARY CHANGES*******************************
*************************************************************************
This section provides a quick reference on all configuration file changes
to be made in order to correctly install ODINSUP.
***IMPORTANT***
A working NDIS configuration should already exist on the workstation that
will be configured using ODINSUP. Then all that needs to be done are
specific changes to each of the four following files as outlined below:
CONFIG.SYS
AUTOEXEC.BAT
PROTOCOL.INI
NET.CFG
Although in some cases additional changes may be required, the following
changes should be sufficient. Refer to specific examples provided for
further clarification or if the following changes are not sufficient.
Note: NETX and VLMs should be interchangeable in configuring ODINSUP
(ODI/NDIS interoperability).
******CONFIG.SYS******
---Remark out the NDIS media driver name
---Set "lastdrive=Z" for VLMs or "lastdrive=?" for NETX, where "?"
represents the drive letter where separation between NDIS and ODI
drives is desired.
******AUTOEXEC.BAT******
---Load LSL and MLID (ODI driver) that replaces the NDIS driver.
---Load ODINSUP just after LSL and MLID and before NETBIND.EXE.
---ODI protocol stacks and Shell (NETX) or Dos Requester (VLMs)
should be loaded after NETBIND.EXE and the NDIS protocol stack(s),
allowing the ODI protocols to be dynamically unloadable (NDIS stacks
are not unloadable).
******PROTOCOL.INI******
---Change all "Bindings=XXXX" so that the XXXX is the ODI driver
name (e.g. "X3C503" in place of "ELNKII"). The "X" in front of the
3 in 3C503 is necessary since the MLID name begins with a number
...not necessary for MLIDs beginning with a letter (e.g. NE2000 or
TOKEN).
******NET.CFG******
---Add "Protocol ODINSUP" line at the top of the NET.CFG. This sets up
ODINSUP as the ODI default protocol stack. Indented on the following
line, place the statement "Bind <MLID>" (e.g. Bind 3C503) to specify
the driver ODINSUP will bind to.
---Beneath the Link Driver XXXX section, the following frame types must be
specified for Ethernet: Ethernet_802.2, Ethernet_II, and Ethernet_SNAP;
for Token-Ring specify: Token-Ring and Token-Ring_SNAP.
---For NDIS protocol stacks requiring larger receive look ahead data sizes
than the MLID maximum, the BUFFERED keyword must be placed below the
Protocol ODINSUP section. There is a detection mechanism that should
report to the user if the "BUFFERED" keyword is needed.
***************************************************************************
*****************SUPPLEMENTAL ODINSUP INFORMATION*************************
***************************************************************************
This section provides more detailed information about ODINSUP configuration
and theory. Also included are a Q & A section followed by several sample
ODINSUP configurations.
Installation of the ODINSUP module is simply a matter of installing it in
memory. In DOS this is accomplished by loading ODINSUP.COM either at the
command line or in a batch file.
All NDIS MAC Drivers should be replaced on the node with their corresponding
ODI LAN Drivers. For example, if you were currently using the ELNKII.DOS
NDIS MAC Driver you would now use the 3C503.COM driver.
Configuration of ODINSUP is accomplished by adding statements to the system
NET.CFG. ODINSUP only needs to be loaded once since it can handle multiple
ODI LAN Drivers from the same module memory image.
The NDIS PROTOCOL.INI file is still necessary to tell the NDIS Protocol(s)
which MAC it should bind to and use. No ODINSUP specific information is
necessary in the PROTOCOL.INI file. However, some MLID information must be
added as detailed above in the "NECESSARY CHANGES" section.
At this time ODINSUP will only support Ethernet and Token-Ring compatible
ODI LAN Drivers. ODINSUP requires that the underlying Ethernet or
Token-Ring ODI LAN Drivers have a number of frame types enabled. For
Ethernet ODI LAN Drivers the ETHERNET_802.2, ETHERNET_SNAP, and ETHERNET_II
frames types must be enabled. For Token-Ring ODI LAN Drivers the TOKEN-RING,
and TOKEN-RING_SNAP frames types must be enabled. Enabling frame types is
accomplished by specifying the frame keyword under the appropriate ODI LAN
Drivers section header. For example:
Sample NET.CFG commands showing enabling of frame types:
link driver ne1000
frame ethernet_802.3
frame ethernet_802.2
frame ethernet_snap
frame ethernet_ii
If no binding information is present in the NET.CFG, ODINSUP will attempt to
locate an Ethernet or Token-Ring ODI LAN Driver. If found, ODINSUP will
attempt to bind to it. Support for more than one ODI LAN Driver or the need
to explicitly specify which ODI LAN Driver to bind to is accomplished by
placing binding information in the NET.CFG. ODINSUP can be bound to a
maximum of four ODI LAN Drivers.
If the default action of ODINSUP is not desired, binding information should
be placed in the NET.CFG to tell ODINSUP which ODI LAN Drivers it should
bind to.
Bind entries specify the name of the ODI LAN Driver and optionally the
instance number. The name of the ODI LAN Driver is normally the name of
the ODI LAN Driver's file (e.g. NE1000 for NE1000.COM). The instance
number may be necessary in cases where more than one type of adapter is
installed in the node (e.g. Two 3C523 adapters). If an instance value is
not specified, ODINSUP will default to the first ODI LAN Driver found
(e.g. If two 3C523 adapters were present, ODINSUP would bind to the first
loaded instance of the ODI LAN Driver). The lowest instance value is 1.
Sample NET.CFG commands under DOS showing assignment of the instance number:
protocol ODINSUP
bind ne1000 ;Bind to the first instance of the NE1000 ODI LAN Driver
bind 3c523 2 ;Bind to the second instance of the 3C523 ODI LAN Driver
bind token 1 ;Bind to the first instance of the TOKEN ODI LAN Driver
OTHER SAMPLE FILES
AUTOEXEC.BAT:
lsl
3c503
ODINSUP
...Load NDIS Protocols if not loaded in CONFIG.SYS
netbind
...Load ODI Protocols
The PROTOCOL.INI must specify sections for each NDIS protocol used. Part of
this information is the Bindings statement which